This adds a new task type for fast vnode restore.

Relates: #4200

* feat(1-1-restore): adds new 1-1-restore sub command

This introduces new cli sub command for the 1-1-restore

Relates: #4200

…equal (#4230)

feat(1-1-restore): validates if source and target clusters nodes are equal

This adds a validation stage for 1-1-restore. The logic is as follows:
- Collect node information for the source cluster from backup manifests
- Collect node information for the target cluster from the Scylla API
- Compare each source node with its corresponding target node

Apart from that nodes-mapping param is validated to ensure that each node has exactly one mapping.

Refs: #4201

feat(1-1-restore): adds copy data stage + loadSStables call

This adds copy data stage for the 1-1-restore with simple integration
test. Data is copied by each node, table by table and after each table
loadSStables is called.
Note: integration tests with TABLETS=enabled will be skipped as 1-1-restore should only
work with v-nodes.

Refs:  #4202 #4203

This adds support for restoring views in 1-1-restore.
Views should be dropped before copy data stage and then re-created to
avoid data inconsistency between base table and view.

Refs: #4252

…l filtering only (#4256)

This reduces functionality of `--keyspace` parameter to support only:
 - keyspace level filtering. Table level filtering (system.table_name) is forbidden.
 - only include filtering. Excluding(!) is forbidden.
 - wildcards (*) are forbidden. The only exception is when the only filter that is provided is a single character (*),
meaning that all keyspaces should be included into restore process.
This is done by allowing to filter on keyspaces that are already exists in the cluster.

Refs: #4253

feat(1-1-restore): sets tombstone_gc mode to repair

This adds skipping of local system tables - the same way we have in
regular restore service.

This sets tombstone_gc mode to 'repair' to avoid data resurrection.
If tables mode is already 'repair', 'disabled' or 'immediate', then it won't be changed.

Refs: #4258

This adds progress tracking of various 1-1-restore stage.
Each progress update represented by RunProgress model saved into db.
w.getProgress is used to aggregate current task progress by Keyspaces,
Tables and Hosts.